Release Summary 25.10 | May 15, 2025
The following key features and improvements, along with bug fixes, have been released in Algonomy CXP products in the release version 25.10.
Enterprise Dashboard
Dynamic Experience Reporting Enhancements
The Dynamic Experience reporting has been enhanced for improved usability and data clarity. Users can now sort table rows alphabetically by default, and a new column has been added to indicate whether each row represents an experience or a variation, making it easier to filter in exports. A currency column has also been introduced to support multi-currency reporting, and the dollar sign has been removed from the Sales column to avoid confusion.
Jira: ENG-29733
Experience Browser Persistence Across Pages
The Experience Browser now stays active as users navigate across multiple pages, eliminating the need to reload each page with the cfrad parameter. Once initiated, the browser remains enabled for 1 day using local storage, improving workflow efficiency. Users also have the option to hide the browser via the menu when needed.
Jira: ENG-30226
Sync R3_COMMON Parameters Between p13n and client.js
To support post-insert JavaScript in client.js implementations where p13n is already integrated, R3_COMMON parameters are now synchronized between the two. If a parameter is not explicitly set in client.js, it will fall back to the value available in p13n. This ensures accurate parameter passing across API calls. The sync covers key fields such as r3_env, pref, atcid, categoryId, cn, searchTerm, and channelId. This update improves consistency across integrations and simplifies client-side setup.
Jira: ENG-30150
Recommend
Strategy Backfill Now Fills to Max Item Count
Strategy backfill logic has been enhanced to continue filling recommendations up to the placement’s maximum item count, instead of stopping at the minimum. This ensures more consistent and complete placements, especially when initial strategies return fewer items. Backfill strategies are now applied in sequence until the configured max count is reached or no more strategies are available. This improvement makes placement configuration more flexible and reliable.
Jira: ENG-30080
Other Feature Enhancements
The following feature enhancements and upgrades have been made in the release version 25.10.
|
Jira # |
Module/Title |
Summary |
General Availability |
|---|---|---|---|
|
Recommend: Support for Logging Request Currency in Recommendation APIs |
Recommendation APIs now support logging the currency specified in the request instead of defaulting to the region’s currency. A new currency parameter is available in the recsForPlacements, p13n_generated, and recs for email APIs. When provided, this currency value is logged in Avro format, enabling better support for cross-region shopping and future reporting use cases. |
15-May-25 |
|
|
Recommend: Privacy Mode Enhancement: MVT Treatment Assignment Now Included with RCS |
To support privacy-compliant user flows, we now include MVT treatment assignments with the RCS even when privacy mode is enabled. This ensures consistency in test assignments, particularly in cases like Abercrombie’s setup, where the RCS is preserved before and after consent. |
15-May-25 |
|
|
Enterprise Dashboard: Multi-Seed Product Selection Support in Recs Test Drive |
Recs Test Drive now supports previewing recommendations using multiple seed products. Users can select multiple products via the product widget, view selected items below, and remove them individually if needed. A pipe-delimited list of product IDs can also be used for bulk entry. Clicking ‘Reset’ clears all selected products. |
15-May-25 |
|
|
Platform: Omnichannel Feed Process Converted to Airflow DAG |
The existing omnichannel feed process has been successfully converted and executed as an Airflow DAG. Offline data is now being processed as expected, and offline purchases are visible in the generated Avro files. |
15-May-25 |
Bug and Support Fixes
The following issues have been fixed in the release version 25.10.
|
Jira # |
Module/Title |
Summary |
General Availability |
|---|---|---|---|
|
Social Proof: Variation Forcing with forceVarId in Social Proof |
Resolved an issue where the forceVarId parameter in Social Proof API was not consistently forcing the intended variation when multiple variations were present. The fix ensures that the correct variation is applied reliably when specified. |
15-May-25 |
|
|
Social Proof: Incorrect Experience ID Logged in Multi-Experience Setup |
When social proof message is rendered through client-side integration, the trackExperience API always logged the last experience it called when multiple valid experiences exists. The fix ensures that when multiple Social Proof experiences are rendered, each experience correctly passes its respective experience ID in the tracking call. |
15-May-25 |
|
|
Lookup Data Encoding Issue in Production |
Resolved an issue where the import_labels_to_s3 process was generating corrupted dimension data for certain sites in production. The fix ensures proper encoding and reliable data transfer to the S3 destination. |
15-May-25 |